Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@components/waves/drops/participation/ParticipationIdentityProfileCard.tsx`:
- Around line 165-170: The extra top margin is always applied because the
wrapper div around IdentityProfileSupplement is rendered even when the
supplement is null; update the JSX to render the wrapper (and
IdentityProfileSupplement) only when the profile actually has content to show —
e.g. guard with a condition like profile?.bio || (profile?.categories &&
profile.categories.length > 0) before rendering the div so that
IdentityProfileSupplement (and its margin via className using isChat) only
appears when there is real supplement content.

In `@components/waves/leaderboard/identity/WaveLeaderboardIdentity.tsx`:
- Around line 134-142: The wrapper div with class "tw-mt-2" is rendered whenever
profile is non-null even if IdentityProfileSupplement returns null, leaving an
empty gap; change the rendering to first compute/check the supplement output (or
a predicate like hasSupplement) for the given profile and only render the
wrapper and IdentityProfileSupplement when that supplement is non-null/true
(i.e., replace the current profile-only guard with a guard that checks both
profile and that IdentityProfileSupplement would render content), referencing
IdentityProfileSupplement and the profile variable to locate the code to update.

In `@openapi.yaml`:
- Around line 10430-10432: The OpenAPI schema uses "type: number" with "format:
int64" (e.g., the rep field in ApiProfileRepCategorySummary) which causes
codegen to emit floats; update these fields to "type: integer" with "format:
int64" across openapi.yaml. Search for fields with "format: int64" (such as rep
in ApiProfileRepCategorySummary) and change their "type" from "number" to
"integer" so generators produce 64-bit integer types (Long/int64) consistently.

---

Nitpick comments:
In `@components/waves/drops/identity/IdentityProfileSupplement.tsx`:
- Around line 66-71: Sanitize maxRepCategories before slicing: ensure
maxRepCategories is treated as a finite non-negative integer (e.g., if it's
undefined keep current behavior, otherwise clamp via Math.max(0,
Math.floor(Number(maxRepCategories))) or similar) and use that sanitized value
when computing visibleRepCategories and hiddenRepCategoryCount so negative, NaN,
fractional, or infinite inputs do not produce surprising slices; update the
logic around visibleRepCategories, maxRepCategories, repCategories, and
hiddenRepCategoryCount to use the clamped integer.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@components/waves/leaderboard/grid/WaveLeaderboardGridItem.tsx`:
- Around line 260-267: The keydown handler that opens the grid item must use the
same gating as the click handler: when handling Enter/Space in the container
(the handler near lines 273-279, e.g., the onKeyDown or keyboard-open logic),
call canOpenGridItemFromClick({ isMenuOpen: showMobileContentOnlyActions &&
isActive, target: event.target as HTMLElement }) and only proceed to
preventDefault() and open the grid item if that returns true; otherwise allow
the nested control (anchor/button) to handle the key event. Update the keyboard
branch to mirror the onCardClick flow (use the same function names
canOpenGridItemFromClick and onCardClick semantics) so author links and footer
action buttons do not get suppressed by preventDefault().

In `@components/waves/winners/podium/WavePodiumItem.tsx`:
- Around line 138-139: Replace the fallback for profile identity in
getAuthorProfileLabel so it uses the author's primary_address instead of id:
locate the getAuthorProfileLabel function and change the fallback expression
from drop.author.id to drop.author.primary_address (i.e., return
drop.author.handle ?? drop.author.primary_address) so profile links and tooltips
match the winners flow (see DefaultWaveWinnerDropSmall usage).

In `@helpers/ProfileHelpers.ts`:
- Around line 88-106: The equality helper currently falls through to
handle/address checks when both normalized ids exist but differ; change the
logic around normalizeProfileTarget(left.id)/right.id so that if both leftId and
rightId are present and equal you return true, but if both are present and NOT
equal you return false immediately (a hard mismatch) instead of checking
handle/primary_address; update the block in ProfileHelpers (the section using
normalizeProfileTarget for left.id/right.id) to enforce this early-false
behavior and leave the subsequent handle and primary_address comparisons
unchanged.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@components/waves/leaderboard/identity/WaveLeaderboardIdentity.tsx`:
- Around line 76-78: The wrapper <div className={className}> in
WaveLeaderboardIdentity still renders even when WaveLeaderboardIdentitySummary
returns null; change WaveLeaderboardIdentity to short-circuit and return null
when the summary would be empty by reusing the same condition (profile &&
!showIdentityHeader && !hasSupplementContent) or by computing a local boolean
(e.g., hasIdentityContent) before rendering; if hasIdentityContent is false,
return null from the WaveLeaderboardIdentity component so the styled wrapper
(className) is not rendered and layout-affecting classes are not applied
unnecessarily.

In `@components/waves/winners/podium/WavePodiumItemContentOutcomes.tsx`:
- Around line 75-112: The JSX lists nicOutcomes, repOutcomes, and manualOutcomes
use non-unique keys (key={`NIC-${nicOutcome.value}`},
key={`REP-${repOutcome.category}-${repOutcome.value}`},
key={`MANUAL-${outcome.description}`}) which can collide when duplicate values
exist; update the key generation to include the iteration index or a unique id
(e.g., map((item, idx) => ... key={`NIC-${nicOutcome.value}-${idx}`}) ) for each
map to guarantee uniqueness and avoid React reconciliation issues in the
components rendering these arrays (nicOutcomes, repOutcomes, manualOutcomes).

---

Nitpick comments:
In `@components/waves/drops/identity/IdentityProfileSupplement.tsx`:
- Around line 76-86: The key for the chips in visibleRepCategories.map uses
`${category.category}-${category.rep}` which can collide; change the key in the
map (inside visibleRepCategories.map) to include the item index as a fallback
(e.g., `${category.category}-${category.rep}-${index}`) so keys are unique, and
also remove the unintended leading space inside the category span (the text node
before {category.category}) to avoid extra spacing; update references in the
same JSX block where formatSignedRep(category.rep) is used.

In `@components/waves/drops/participation/ParticipationIdentityProfileCard.tsx`:
- Around line 83-84: The prop _supplementFullWidth (originally
supplementFullWidth) in ParticipationIdentityProfileCard is currently unused —
either remove it from the component props/interface to avoid dead API surface,
or keep it and add a short inline comment/TODO explaining it's intentionally
unused for now and will be implemented later; update the prop list
(showIdentityHeader, supplementFullWidth/_supplementFullWidth) and any related
types accordingly so the intent is clear.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@components/waves/winners/podium/WavePodiumItem.tsx`:
- Around line 254-256: The author profile URL is being built manually as
`/${authorProfileLabel}`, causing inconsistent casing/encoding; replace that
with the canonical helper used elsewhere by calling getIdentityHref(...) instead
of string interpolation (use getIdentityHref(authorProfileLabel) or the same
argument shape used elsewhere in this file) so authorProfileHref is generated
via getIdentityHref; keep authorProfileLabel and authorTooltipUser as-is but use
getIdentityHref to construct authorProfileHref.
- Around line 283-312: The avatar branch for identityDisplay/profileUser removes
the profile Link, causing inconsistent navigation and an unnamed control for
screen readers when pfp is missing; update the JSX so both branches wrap
PodiumAvatar with a Link to the profile when a profile href/label exists (use
authorProfileHref/authorProfileLabel or primary equivalents), and add an
explicit accessible name by setting aria-label on the Link (or ensuring
PodiumAvatar alt is present and not aria-hidden) so screen readers always get
the profile name; modify the identityDisplay/profileUser branch and the fallback
branch around PodiumAvatar/Link to keep behavior and a11y consistent.